Duplicate an existing server environment

The following describes how to duplicate an existing MOMI environment. If the duplicate is on a different NonStop System, a password is required and file placement should be checked but otherwise the files may be used as is. If the duplicate is on the same NonStop System, some changes are necessary as data files cannot be shared.

Take note of the explanations following as avoiding some files may speed up the creation of the duplicate environment.

1. stop the existing MOMI process.

2. using FUP duplicate all of the files in the existing MOMI subvolume to another subvolume.

3. restart the existing MOMI process.

4. In the duplicate OBYMOMI file:

on the same system:

assign a new process name to MOMI (each MOMI process must have unique process name).

on a different system:

change the PASSWORD to one assigned for that system.

5. In the duplicate CONFMOMI file:

on the same system:

for the keyword TCPIP-LISTEN, assign a new port number (each MOMI server must listen on a unique port).

for the keyword HSTnnDB, assign new vol/subvol locations (each MOMI server must have unique history files).

check other data file names to insure make sure they are not duplicated (the keywords above are the most common but a few others exist).

on a different system:

check volume names to insure they are valid on the new system.

The following are brief explanations of certain files within the MOMI subvolume. MOMI automatically creates new one(s) at start up if they are not present:

The CNF01DB file is the MOMI configuration database. It stores configuration information entered online such as Alarm definitions. It does not generally store information found in the OBYMOMI or CONFMOMI files. To start a duplicate environment 'clean', simply delete this file.

The LOG01DB file is the MOMI log file. It stores messages logged by MOMI. If you want to start the duplicate environment with an empty log file, simply delete this file.

The HSTnnDB files are the MOMI history files. If you want to start the duplicate environment with empty history files, simply delete them. These files are usually large and may take some time to duplicate. It is usually faster to duplicate them from one disk volume to another disk volume (to avoid drive thrashing).